Skip to content

Conversation

@MaxyMoos
Copy link

Forward-porting of #1331 (16.0)

@MaxyMoos MaxyMoos force-pushed the 17.0-fix-in_invoice-communication branch from dbf410c to c2b9df8 Compare March 24, 2025 14:01
@MaxyMoos MaxyMoos changed the title [17.0][FIX/IMP] account_payment_order: use payment_reference if present for our payments [17.0][FIX/IMP] account_payment_order: use payment_reference if present for out payments Mar 24, 2025
Copy link
Member

@sbidoul sbidoul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you cherry-pick the original commit in order to preserve the commit message and authorship?

… payments

When a payment reference (field `payment_reference`) is provided on the vendor bill, it should be used in priority over the vendor bill number (field `ref`).

One reason is that the `ref` field is different for each invoice of the same supplier (it is used in Odoo's standard duplicate warning),
but the payment reference maybe the same for all payments to the
same supplier. For instance some suppliers request that the customer
id is used on the payment communication and it is the same on
all their invoices.

Another reason is that some supplier use a structured payment communication scheme, and that one only makes sense in
the payment_reference field.
@MaxyMoos MaxyMoos force-pushed the 17.0-fix-in_invoice-communication branch from c2b9df8 to 4809775 Compare May 2, 2025 16:24
@MaxyMoos
Copy link
Author

MaxyMoos commented May 2, 2025

Well now i'm feeling a bit stupid because it was way simpler but hadn't even crossed my mind! Thanks for the suggestion, it's done.

Copy link
Member

@sbidoul sbidoul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 31, 2025
@pedrobaeza pedrobaeza added this to the 17.0 milestone Sep 1, 2025
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants